fix: properly handle keyword blocking #535
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change(s)
What changed and why
Implemented the new
isContentBlocked()method from FossifyOrg/mmslib#2. This ensures that the received messages are checked for blocked keywords before they are saved to the system database.Note: This could have been fixed easily by filtering out existing messages with blocked keywords at run time, but this way is more consistent with how messages from blocked numbers are dropped.
Tests performed
I couldn't test it, but Aga-C and laubster have confirmed that this works.
Closes the following issue(s)
Checklist
CHANGELOG.md(if applicable).